play makAll work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All
HBAM2016AUG95
Pro 3.0
All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dullCopyright 1984-1996 Claris Corporation
and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy. All work and no play makes Jack a dull boy.
HBAM3016AUG95@
Pro 3.0F!
Sunday
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
January
February
March
April
August
September
October
November
December
1st Quarter
2nd Quarter
3rd Quarter
4th Quarter
chart
8/7/97
CONSTANT
GRAPHICS
LABELS
LABELSINDICATOR
LOTSACRS
LOTSASPACES
Graphics
@YA Pie Chart
Instructions Mac
Instructions PC
GraphicsB
PCLABEL1
PCLABEL2
PCLABEL3
PCLABEL4
PCLABEL5
PCLABEL6
PERCENT1
PERCENT2
PERCENT3
PERCENT4
PERCENT5
PERCENT6
SLICE1
SLICE2
SLICE3
SLICE4
SLICE5
SLICE6
SLICES1
SLICES10
SLICES2
SLICES3
SLICES4
SLICES5
SLICES6
SLICES7
SLICES8
SLICES9
SOLIDCHECK
TOTALVALUE
7 VARIABLE1
VARIABLE2
VARIABLE3
VARIABLE4
VARIABLE5
VARIABLE6
Slices2B
Slices3B
Slices4B
Slices5B
Slices1B
Slices6B
A Variable1B
A Variable2B
A Variable3B
A Variable4B
A Variable5B
A Variable6B
GraphicsB
Slices7B
Slices8B
Slices9B
Slices10B
TotalValueB
Percent1B
100 *
Percent2B
100 *
Percent3B
100 *
Percent4B
100 *
Percent5B
100 *
Percent6B
100 *
Slice1B
Slice2B
Slice3B
Slice4B
Slice5B
Slice6B
PCLabel1B
p = "yes"
031416)*43)
7(" "
)) &
031416)*124)
PCLabel2B
p = "yes"
031416)*43)
7(" "
)) &
031416)*124)
PCLabel3B
PCLabel4B
p = "yes"
031416)*43)
7(" "
)) &
031416)*124)
PCLabel5B
p = "yes"
031416)*43)
7(" "
)) &
031416)*124)
PCLabel6B
p = "yes"
031416)*43)
7(" "
)) &
031416)*124)
p = "yes"
031416)*43)
7(" "
)) &
031416)*124)
LotsaCRsB
SolidCheckB
LotsaSpacesB
LabelsB
LabelsIndicatorB
p = "yes"
ConstantB
A Pie ChartB
Instructions MacB
Instructions PCB
u Pie Chart
v Pie Chart
u Pie Chart
v Pie Chart
General:
Everything in this file is stored in a single record. No globals, relations, or scripts are used in any of the demo files, allowing all the calculations to remain stored and indexable. This gives you the greatest flexibility for incorporating it into your own solutions.
Fields:
Constant A calculation, always 1, for use as a relational key if you decide to link to this file via a relation. Set up another field of 1 in your main file, and you can set the Variable fields usin
g this relation.
LotsaCRs This is just a few hundred carriage returns, which the PCLabel calcs use a certain portion of.
LotsaSpaces Ditto, except these are just a bunch of spaces.
PCLabel1...6 This is a fairly involved polar to Cartesian coordinate conversion to calculate the right number of spaces from the left side, and the right number of lines from the bottom, to exactly position each slice label. If you
re not going to use the slice labels you can delete these fields. If you
need to make more, note that each field must contain a reference to the next highest field also, again except for the last one. If you add a PCLabel7, you must edit PCLabel6 to include it.
Percent1...6 This calculation field gives a cumulative result. For example, if the values for the pie are 2, 2, and 4, these percent fields will come out as 100%, 75%, and 50%. To accomplish this, the calc needs to look at the next higher value. So Percent4 contains references to Variable4
and Variable5. Except for your highest pie piece; since there is no higher value.
Slice1...6 This container field rounds off the Percent field to an integer and loads the corresponding repetition from the master Slices.
Slices1...10 These are the master graphics. Pie slices are provided for 10 colors, each field holds 100 different graphics in repetitions. You don
t need to do anything with these.
TotalValue This is the total of all the variables. If you add variables, make s
ure to adjust this calc to include them.
Variable1...6 These are the values for each slice, which you must set with your data. You can use the Set Field command, a script, a relation, or whatever you want. To use more than six slices, simply add more Number fields and name them Variable7, Variable8, etc.
Layout:
The layout for the pies is very simple. Just stack the Slice1...Slice6 container fields on top of each other, and make sure you keep them transparent so they don
t bloc
k the slices underneath them. The lowest numbered slice must be on the bottom! This is how it works, using 4 of our slices as an example:
Resizing:
You may resize the container fields at will to make the charts whatever size you want. However, doing so will throw off the PCLabel fields, which use constant values to achieve the right positioning for this demo file. To fix this, look at the calculation for PCLabel1:
If(Labels = "yes",
Left(LotsaSpaces,
45+Sin((Percent1+Per
cent2)*.031416)*43)
& Left(" ", 5-Length(Variable1)) & Variable1 &
Left(LotsaCRs,
124+Cos((Percent1+Percent2)*.031416)*124)
, "")
43 in line 3 is the horizontal constant, and 124 in line 6 is the vertical constant. Play with these numbers if you decide to resize. If you make the charts exactly twice the size, change these values to 86 and 428. If you make them too enormous, you may have to add some carriage returns to LotsaCRs or some spaces to LotsaSpaces.
u Pie Chart
v Pie Chart
u Pie Chart
v Pie Chart
General:
Everything in this file is stored in a single record. No globals, relations, or scripts are used in any of the demo files, allowing all the calculations to remain stored and indexable. This gives you the greatest flexibility for incorporating it into your own solutions.
Fields:
Constant A calculation, always 1, for use as a relational key if you decide to link to this file via a relation. Set up another field of 1 in your main file, and you can set the Variable fields usin
g this relation.
LotsaCRs This is just a few hundred carriage returns, which the PCLabel calcs use a certain portion of.
LotsaSpaces Ditto, except these are just a bunch of spaces.
PCLabel1...6 This is a fairly involved polar to Cartesian coordinate conversion to calculate the right number of spaces from the left side, and the right number of lines from the bottom, to exactly position each slice label. If you
re not going to use the slice labels you can delete these fields. If you
need to make more, note that each field must contain a reference to the next highest field also, again except for the last one. If you add a PCLabel7, you must edit PCLabel6 to include it.
Percent1...6 This calculation field gives a cumulative result. For example, if the values for the pie are 2, 2, and 4, these percent fields will come out as 100%, 75%, and 50%. To accomplish this, the calc needs to look at the next higher value. So Percent4 contains references to Variable4
and Variable5. Except for your highest pie piece; since there is no higher value.
Slice1...6 This container field rounds off the Percent field to an integer and loads the corresponding repetition from the master Slices.
Slices1...10 These are the master graphics. Pie slices are provided for 10 colors, each field holds 100 different graphics in repetitions. You don
t need to do anything with these.
TotalValue This is the total of all the variables. If you add variables, make
sure to adjust this calc to include them.
Variable1...6 These are the values for each slice, which you must set with your data. You can use the Set Field command, a script, a relation, or whatever you want. To use more than six slices, simply add more Number fields and name them Variable7, Variable8, etc.
Layout:
The layout for the pies is very simple. Just stack the Slice1...Slice6 container fields on top of each other, and make sure you keep them transparent so they don
ock the slices underneath them. The lowest numbered slice must be on the bottom! This is how it works, using 4 of our slices as an example:
Resizing:
You may resize the container fields at will to make the charts whatever size you want. However, doing so will throw off the PCLabel fields, which use constant values to achieve the right positioning for this demo file. To fix this, look at the calculation for PCLabel1:
If(Labels = "yes",
Left(LotsaSpaces,
45+Sin((Percent1+P
ercent2)*.031416)*43)
& Left(" ", 5-Length(Variable1)) & Variable1 &
Left(LotsaCRs,
124+Cos((Percent1+Percent2)*.031416)*124)
, "")
43 in line 3 is the horizontal constant, and 124 in line 6 is the vertical constant. Play with these numbers if you decide to resize. If you make the charts exactly twice the size, change these values to 86 and 428. If you make them too enormous, you may have to add some carriage returns to LotsaCRs or some spaces to LotsaSpaces.
(.txt)